DynaPay

Description:

DynaPay provides a method of periodically polling transaction-oriented files that are generated from any system to facilitate "near real-time" processing. Typically, these systems are third party applications where the customer does not have access to the source code in order to directly integrate payment processing within the application itself. DynaPay provides a method of integrating payment processing capability with the application without the need to modify the originating application or the output/input files.

Skipjack DynaPay Integration Guide  (*PDF - 0.7 MB)


A typical example is as follows:

1. Operator keys in customer and payment information into client application (e.g. billing system or 3rd party application such as ICVERIFY)
2. DynaPay automatically retrieves data file from system and converts its contents into a format that can be processed by the Skipjack gateway
3. DynaPay submits the converted data file for processing
4. DynaPay retrieves the response file from Skipjack and converts it back to a format that is "readable" by the 3rd party application
5. The 3rd party application retrieves and imports resulting transaction information and associates it with appropriate client data inside of the application database

Features:

• Support for a wide range of applications
• Customizable to meet the specific file format required by the client application (each implementation requires some degree of customization)  
• Credit card numbers are obscured in the Request and Response files
• Supports authorization, refund, void and settlement commands
• Support control over batch settlement details (view and manage batch settlements)
• Includes access to Skipjack's online Transaction Management and Reporting tools
• Supports manual and automatic batch settlement modes

Benefits:

• Provides near real-time payment processing capability without the need to modify the application source code
• Automates the process of processing transactions and updating the source application with the transaction results
• Bank-neutral solution (no application changes required with change of merchant account provider)

Uses:

Used for any application that generates transaction-oriented output files where the user cannot or does not wish to modify the application source code to support payment processing.